Cisco UCS servers and fabric interconnects (hardware) End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Cisco UCS servers and fabric interconnects (hardware) versions. Dates read at the vendor's own lifecycle pages (cisco.com). Updated at every deploy.
Cisco UCS servers and fabric interconnects (hardware) UCS C480 M5 is supported until October 31, 2028, its end-of-support date. The End-of-Sale date for Cisco UCS servers and fabric interconnects (hardware) UCS C480 M5 is October 30, 2023. The next Cisco UCS servers and fabric interconnects (hardware) version to reach end of life is UCS 6332 Fabric Interconnect, on October 31, 2028. 9 of 27 tracked Cisco UCS servers and fabric interconnects (hardware) versions are past end of life; the most recent to reach it, UCS 6248UP Fabric Interconnect, did so on May 31, 2024. The full Cisco UCS servers and fabric interconnects (hardware) lifecycle, with every version's release and end-of-support date, is in the table below.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| UCS C240 M3 | UCS C240 M3 | — | Dec 31, 2021 | 1751 days past EOL | EOL |
| UCS B200 M3 | UCS B200 M3 | — | Dec 31, 2021 | 1751 days past EOL | EOL |
| UCS C460 M4 | UCS C460 M4 | — | Feb 29, 2024 | 961 days past EOL | EOL |
| UCS C240 M4 | UCS C240 M4 | — | Feb 29, 2024 | 961 days past EOL | EOL |
| UCS C220 M4 | UCS C220 M4 | — | Feb 29, 2024 | 961 days past EOL | EOL |
| UCS B420 M4 | UCS B420 M4 | — | Feb 29, 2024 | 961 days past EOL | EOL |
| UCS B200 M4 | UCS B200 M4 | — | Feb 29, 2024 | 961 days past EOL | EOL |
| UCS 6296UP Fabric Interconnect | UCS 6296UP Fabric Interconnect | — | May 31, 2024 | 869 days past EOL | EOL |
| UCS 6248UP Fabric Interconnect | UCS 6248UP Fabric Interconnect | — | May 31, 2024 | 869 days past EOL | EOL |
| UCS C480 M5 | UCS C480 M5 | — | Oct 31, 2028 | 745 days remaining | Active |
| UCS C240 M5 | UCS C240 M5 | — | Oct 31, 2028 | 745 days remaining | Active |
| UCS C220 M5 | UCS C220 M5 | — | Oct 31, 2028 | 745 days remaining | Active |
| UCS B200 M5 | UCS B200 M5 | — | Oct 31, 2028 | 745 days remaining | Active |
| UCS 6332-16UP Fabric Interconnect | UCS 6332-16UP Fabric Interconnect | — | Oct 31, 2028 | 745 days remaining | Active |
| UCS 6332 Fabric Interconnect | UCS 6332 Fabric Interconnect | — | Oct 31, 2028 | 745 days remaining | Active |
| UCS C885A M8 with NVIDIA HGX H200 | UCS C885A M8 with NVIDIA HGX H200 | — | Jun 30, 2029 | 987 days remaining | Active |
| UCS C885A M8 with AMD MI300X | UCS C885A M8 with AMD MI300X | — | Jun 30, 2029 | 987 days remaining | Active |
| UCS C885A M8 with NVIDIA HGX H100 | UCS C885A M8 with NVIDIA HGX H100 | — | Jul 31, 2030 | 1383 days remaining | Active |
| UCS C240 M6 | UCS C240 M6 | — | Sep 30, 2030 | 1444 days remaining | Active |
| UCS C220 M6 | UCS C220 M6 | — | Sep 30, 2030 | 1444 days remaining | Active |
| UCS B200 M6 | UCS B200 M6 | — | Dec 31, 2030 | 1536 days remaining | Active |
| UCS 6324 Fabric Interconnect | UCS 6324 Fabric Interconnect | — | Dec 31, 2030 | 1536 days remaining | Active |
| UCS 5108 chassis (AC2) | UCS 5108 chassis (AC2) | — | Dec 31, 2030 | 1536 days remaining | Active |
| UCS C245 M6 | UCS C245 M6 | — | Jun 30, 2031 | 1717 days remaining | Active |
| UCS C225 M6 | UCS C225 M6 | — | Jun 30, 2031 | 1717 days remaining | Active |
| UCS 64108 Fabric Interconnect | UCS 64108 Fabric Interconnect | — | Dec 31, 2031 | 1901 days remaining | Active |
| UCS 6454 Fabric Interconnect | UCS 6454 Fabric Interconnect | — | Dec 31, 2031 | 1901 days remaining | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/cisco-ucs)
Cisco UCS servers and fabric interconnects (hardware) lifecycle status — the real story
Cisco Unified Computing System (UCS) is Cisco's data-centre server line: the B-Series blade servers and 5108 chassis, the C-Series rack servers (M3 to M6), the C885A M8 GPU servers with NVIDIA HGX H100, NVIDIA HGX H200 or AMD MI300X, and the 6200, 6300 and 6400 series fabric interconnects. Cycles on this page are server and fabric-interconnect models. Every date comes from Cisco's own End-of-Sale and End-of-Life bulletins on cisco.com (public, no login), one bulletin per family, each cited on its cycles. Each bulletin was read twice on 2026-10-16: the bulletin HTML fetched with a browser header set and the same bulletin in the built-in browser; every milestone identical (tools/cisco-hardware-bulletins.mjs refuses to write on any difference). Cycles are models; each lists the chassis part numbers Table 2 of its bulletin retires (base, spare and bundle forms). A model gets a cycle only when its own chassis part number is in Table 2; where Cisco titles a bulletin select, the cycles are the exact part numbers it retires. Current models without a bulletin are not listed; their absence is not a statement that they are supported indefinitely.
Field mapping, the Cisco hardware convention of the Cisco ASA 5500-X and Cisco RV pages: support is Cisco's End-of-Sale Date ('The last date to order the product through Cisco point-of-sale mechanisms'); eol is Cisco's Last Date of Support ('The last date to receive applicable service and support for the product as entitled by active service contracts or by warranty terms and conditions. After this date, all support services for the product are unavailable, and the product becomes obsolete'). The other Table 1 milestones (End-of-Life Announcement, Last Ship, End of SW Maintenance Releases, End of Vulnerability/Security Support, End of Routine Failure Analysis, End of New Service Attachment, End of Service Contract Renewal) are carried under their own names where the bulletin prints them; a milestone the bulletin does not print is empty. Cisco bulletins print no launch date, so releaseDate is empty.
The B260 M4 and B460 M4 named in the title of the B-Series M4 bulletin have no base part number of their own in its Table 2 and are not listed. The B480 M5 bulletin address returns a 404 page. M7 and M8 general-purpose servers have no bulletin yet. The C885A rows date the Cisco server, not the NVIDIA or AMD accelerators; NVIDIA publishes no end-of-life date for the H100 or H200 GPUs.
Cisco UCS servers and fabric interconnects (hardware) release and support pattern
Of the 27 release lines tracked, 9 are past end of life and 18 are still within support. The next scheduled end of life is UCS 6332 Fabric Interconnect on October 31, 2028 — 744 days from this build. The longest-supported line currently published is UCS 64108 Fabric Interconnect, to December 31, 2031.
Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.
What does Cisco UCS servers and fabric interconnects (hardware) end of life mean for your organization?
When a version of Cisco UCS servers and fabric interconnects (hardware) reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no vendor patch is coming. This is one of the most dangerous gaps in enterprise security posture.
Organizations running EOL Cisco UCS servers and fabric interconnects (hardware) should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Your options when Cisco UCS servers and fabric interconnects (hardware) reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Buy extended support | Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application | A bridge, not a destination — every year purchased is a year the migration still has to happen |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
Formalizing decisions like this across your estate? Our free EOL policy template is a ready-to-adopt policy with risk tiers, remediation SLAs, and audit mapping — no signup, free to use and share.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Cisco UCS servers and fabric interconnects (hardware) versions. This is a bridge, not a permanent solution — plan your migration in parallel.
Cisco UCS servers and fabric interconnects (hardware) has 9 versions past end of life — security patches have stopped, but CVE disclosures haven't. Extended support past the official date exists for many products in this position — whether it exists for Cisco UCS servers and fabric interconnects (hardware) is exactly what we check. Tell us where to reach you and we'll reply with matched options and pricing guidance — or an honest "no vendor covers this."